Remove assert on ARCH_NAME in data collection step in workflows#37300
Merged
Remove assert on ARCH_NAME in data collection step in workflows#37300
Conversation
3 tasks
b675b7f to
cb0d360
Compare
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 6, 2026
Change galaxy demo pipeline to use [reorganized pipeline](https://tenstorrent.atlassian.net/wiki/spaces/MI6/pages/1396506680/Proposed+pipeline+and+test+organization+changes) format. - format Galaxy Demo Pipeline to use `*tests.yaml` and time budgets - format Galaxy Demo Pipeline to use `.github/sku_config.yaml` to map SKUs in `*tests.yaml` to machine `runs-on` labels for infra team use - removes `ARCH_NAME` from workflow This PR does not affect how the pipeline is used. Only affects adding tests in the future. **About pipeline reorg:** Devs should only have to interface with tests/pipeline_reorg/*tests.yaml to add their tests instead of adding them directly to the github actions workflow files. Tests are subject to a team budget .github/time_budget.yaml that dictates budgets per team, per pipeline, per SKU aka machine type (eg. n150, t3k, p150, etc). Team names and budgets are in flux - please message me if you have any concerns. Testing - [x] Select 1 test https://github.com/tenstorrent/tt-metal/actions/runs/21732479327 - [x] Select all tests https://github.com/tenstorrent/tt-metal/actions/runs/21732581550 ARCH_NAME related failures in Save Environment Data step is addressed in #37300 The tests themselves still pass - [x] Invoke from Galaxy select your own pipeline https://github.com/tenstorrent/tt-metal/actions/runs/21732620140
williamlyTT
reviewed
Feb 6, 2026
williamlyTT
reviewed
Feb 6, 2026
williamlyTT
reviewed
Feb 6, 2026
williamlyTT
approved these changes
Feb 6, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Removes the workflow’s hard dependency on ARCH_NAME by updating the benchmark environment data-collection code to infer device type from runner metadata (CIv2 runner naming) or repo config (CIv1 SKU config), and updates the Galaxy demo workflow to stop exporting ARCH_NAME.
Changes:
- Add device type inference logic (
RUNNER_NAME/.github/sku_config.yaml) and remove the hardARCH_NAMEassert in benchmark environment JSON creation. - Refactor repo-root path resolution used by benchmark artifact discovery.
- Comment out
ARCH_NAMEinjection in the Galaxy demo workflow container environment.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
infra/data_collection/github/utils.py |
Adds device-type inference and removes hard ARCH_NAME requirement for environment completion; refactors repo-root path usage. |
.github/workflows/galaxy-demo-tests-impl.yaml |
Stops exporting ARCH_NAME into the container environment for Galaxy demo jobs. |
66e151f to
95f9364
Compare
…benchmark_with_environment_json.py needs the install
williamlyTT
reviewed
Feb 6, 2026
Co-authored-by: William Ly <williamly@tenstorrent.com>
| sku_config_path = _get_repo_root() / ".github" / "sku_config.yaml" | ||
| if sku_config_path.exists(): | ||
| with open(sku_config_path) as f: | ||
| config = yaml.safe_load(f) |
There was a problem hiding this comment.
yaml.safe_load(f) can return None (e.g., empty YAML file), in which case config.get(...) will raise an AttributeError. Consider defaulting to an empty dict (e.g., config = yaml.safe_load(f) or {}) before accessing .get() to make the inference logic robust.
Suggested change
| config = yaml.safe_load(f) | |
| config = yaml.safe_load(f) or {} |
adrian-pascual-bernal
pushed a commit
that referenced
this pull request
Feb 10, 2026
Change galaxy demo pipeline to use [reorganized pipeline](https://tenstorrent.atlassian.net/wiki/spaces/MI6/pages/1396506680/Proposed+pipeline+and+test+organization+changes) format. - format Galaxy Demo Pipeline to use `*tests.yaml` and time budgets - format Galaxy Demo Pipeline to use `.github/sku_config.yaml` to map SKUs in `*tests.yaml` to machine `runs-on` labels for infra team use - removes `ARCH_NAME` from workflow This PR does not affect how the pipeline is used. Only affects adding tests in the future. **About pipeline reorg:** Devs should only have to interface with tests/pipeline_reorg/*tests.yaml to add their tests instead of adding them directly to the github actions workflow files. Tests are subject to a team budget .github/time_budget.yaml that dictates budgets per team, per pipeline, per SKU aka machine type (eg. n150, t3k, p150, etc). Team names and budgets are in flux - please message me if you have any concerns. Testing - [x] Select 1 test https://github.com/tenstorrent/tt-metal/actions/runs/21732479327 - [x] Select all tests https://github.com/tenstorrent/tt-metal/actions/runs/21732581550 ARCH_NAME related failures in Save Environment Data step is addressed in #37300 The tests themselves still pass - [x] Invoke from Galaxy select your own pipeline https://github.com/tenstorrent/tt-metal/actions/runs/21732620140
adrian-pascual-bernal
pushed a commit
that referenced
this pull request
Feb 10, 2026
We would like to gradually remove reliance on `ARCH_NAME` env var. Recently `ARCH_NAME` was removed from Galaxy demo pipelines. No tests need the env var set, but the data collection step in the workflow still has an assert on `ARCH_NAME`. This PR removes the hard assert on `ARCH_NAME` in the data collection script and tries to infer from the runner name for CIv2 or the SKU config for CIv1. Testing: - [x] Galaxy demo https://github.com/tenstorrent/tt-metal/actions/runs/21768966673 --------- Co-authored-by: William Ly <williamly@tenstorrent.com>
ssundaramTT
pushed a commit
that referenced
this pull request
Feb 10, 2026
Change galaxy demo pipeline to use [reorganized pipeline](https://tenstorrent.atlassian.net/wiki/spaces/MI6/pages/1396506680/Proposed+pipeline+and+test+organization+changes) format. - format Galaxy Demo Pipeline to use `*tests.yaml` and time budgets - format Galaxy Demo Pipeline to use `.github/sku_config.yaml` to map SKUs in `*tests.yaml` to machine `runs-on` labels for infra team use - removes `ARCH_NAME` from workflow This PR does not affect how the pipeline is used. Only affects adding tests in the future. **About pipeline reorg:** Devs should only have to interface with tests/pipeline_reorg/*tests.yaml to add their tests instead of adding them directly to the github actions workflow files. Tests are subject to a team budget .github/time_budget.yaml that dictates budgets per team, per pipeline, per SKU aka machine type (eg. n150, t3k, p150, etc). Team names and budgets are in flux - please message me if you have any concerns. Testing - [x] Select 1 test https://github.com/tenstorrent/tt-metal/actions/runs/21732479327 - [x] Select all tests https://github.com/tenstorrent/tt-metal/actions/runs/21732581550 ARCH_NAME related failures in Save Environment Data step is addressed in #37300 The tests themselves still pass - [x] Invoke from Galaxy select your own pipeline https://github.com/tenstorrent/tt-metal/actions/runs/21732620140
ssundaramTT
pushed a commit
that referenced
this pull request
Feb 10, 2026
We would like to gradually remove reliance on `ARCH_NAME` env var. Recently `ARCH_NAME` was removed from Galaxy demo pipelines. No tests need the env var set, but the data collection step in the workflow still has an assert on `ARCH_NAME`. This PR removes the hard assert on `ARCH_NAME` in the data collection script and tries to infer from the runner name for CIv2 or the SKU config for CIv1. Testing: - [x] Galaxy demo https://github.com/tenstorrent/tt-metal/actions/runs/21768966673 --------- Co-authored-by: William Ly <williamly@tenstorrent.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We would like to gradually remove reliance on
ARCH_NAMEenv var.Recently
ARCH_NAMEwas removed from Galaxy demo pipelines. No tests need the env var set, but the data collection step in the workflow still has an assert onARCH_NAME.This PR removes the hard assert on
ARCH_NAMEin the data collection script and tries to infer from the runner name for CIv2 or the SKU config for CIv1.Testing: